<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title>Velocitime Minutes 4</title>
             
  <meta http-equiv="content-type"
 content="text/html; charset=ISO-8859-1">
       
  <meta name="author" content="robert">
</head>
  <body>
   
<h1>Velocityme Minutes 4</h1>
   
<table cellpadding="2" cellspacing="0" border="1" width="100%">
    <tbody>
      <tr>
        <th valign="top" bgcolor="#cccccc">Date<br>
        </th>
        <th valign="top" bgcolor="#cccccc">Venue<br>
        </th>
        <th valign="top" bgcolor="#cccccc">Present<br>
        </th>
        <th valign="top" bgcolor="#cccccc">Apologies<br>
        </th>
      </tr>
      <tr>
        <td valign="top">2002-08-27<br>
 19h45-22h06<br>
        </td>
        <td valign="top">22 Bordeaux<br>
  Tokai Villas<br>
        </td>
        <td valign="top">Robert Crida (RC)<br>
  Barry Radloff (BR)<br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
       
  </tbody>  
</table>
  <br>
   
<table width="100%" border="0" cellspacing="0" cellpadding="2">
    <tbody>
      <tr>
        <th valign="top" bgcolor="#cccccc">Topic<br>
        </th>
        <th valign="top" bgcolor="#cccccc">Responsible Person<br>
        </th>
        <th valign="top" bgcolor="#cccccc">Due Date<br>
        </th>
      </tr>
      <tr>
        <td valign="top"><b>1. Matters arising</b><br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">1.1 BR noted that the previous fortnight had been 
very hectic and apologised for lack of preparation but noted that the situation 
should improve next week.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top"><b>2. Accept minutes from previous meeting</b><br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
           <tr>
        <td valign="top">2.1 BR to read starting point document by next meeting<br>
        </td>
        <td valign="top">BR<br>
        </td>
        <td valign="top">2002-09-03<br>
        </td>
      </tr>
      <tr>
        <td valign="top">2.2 BR apologises for not sending project space
demo to RC, it got lost during a harddisk crash<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">2.3 BR to resend previous minutes with SWOT analysis 
attachments and RC goals and visions<br>
        </td>
        <td valign="top">BR<br>
        </td>
        <td valign="top">2002-09-03<br>
        </td>
      </tr>
      <tr>
        <td valign="top"><b>3. Including other people in the project</b><br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">3.1 Proposed by RC that other people could be involved 
in the project. BR agrees but notes that we need to discuss what roles we 
are lacking to augment out skills.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">3.2 RC has spoken briefly to Wayne Paverd (WP) to 
find out his plans for the future without mentioning Veloocityme. He is considering 
his options. RC commented that he would be a very good resource but possibly 
a low realistic possibility of getting him. RC will approach him in confidence 
if it seems appropriate at the time. We should at least maintain contact with
him.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">3.3 John Spence (JS) has indicated to RC that he 
is happy to attend meetings occasionally to help us evaluate our progress.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">3.4 BR asked if we needed to speak to other people 
to get advice on additional people/skills.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">3.5 RC noted that the current target is an internal 
software prototype and that business skills are not necessarily appropriate 
at this point. Perhaps when we set a longer term goal it would be a more appropriate
time to consider additional skills required.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">3.6 RC noted that at this stage we can learn new 
skills for software development to fill gaps. The advantage of additional 
people is a broader range of knowledge and a larger workforce to get the job
done more quickly.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">3.7 RC proposed that we wait until the need for
additional members comes up or an opportunity presents itself.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top"><b>4. Quality control</b><br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">4.1 The following project lifeline was agreed upon:<br>
       
      <ol>
         <li>User requirements</li>
         <li>Functional specification (captures user requirements through 
use case analysis and should be completed before next step. Note that it should
address every point in the user requirements)</li>
         <li>Technical specification (design)</li>
         <li>Implementation</li>
         <li>Testing</li>
         <li>Deployment</li>
       
      </ol>
 Note that steps 3-6 are typically going to iterate. Once we reach step 6 
for the first time it will be labelled as v1.0. Corrections after that will 
result in minor version updates.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top"><b>5. Software configuration</b><br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
      <tr>
        <td valign="top">5.1 The topic of which software development tool 
should be used was discussed. BR proposed that Borland JBuilder was well supported
but would have to be bought. RC indicated that Roy Emmerich (RE) was using
NetBeans which is free and was not having any problems with it. It was agreed
that in the short term (v1.0) NetBeans would be adequate for development.
After that time the development tool could be reevaulated.<br>
        </td>
        <td valign="top"><br>
        </td>
        <td valign="top"><br>
        </td>
      </tr>
     <tr>
       <td valign="top">5.2 BR proposed that we only begin to use revision 
control when modules are completed due to the lack of a centralised server. 
We would require a more formal revision control system once v1.0 was ready 
for deployment.<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">5.3 It was agreed that v1.0 would be complete when 
it had met the following requirements:<br>
       
      <ol>
         <li>It was stored under revision control</li>
         <li>It could be built automatically and successfully from the revision 
control system</li>
         <li>It meets the v1 functionality scope</li>
         <li>Modules are unit tested where practical</li>
         <li>Functional testing passes based on function spec</li>
         <li>System testing (performed by David Spencer (DS) and RE) passes<br>
         </li>
       
      </ol>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">5.4 RC proposed that we investigate using ANT for 
automatic configuration building<br>
       </td>
       <td valign="top">BR, RC<br>
       </td>
       <td valign="top">open<br>
       </td>
     </tr>
     <tr>
       <td valign="top">5.5 The following coding style standards were accepted:<br>
       
      <ul>
         <li>The normal Java coding style standards would apply to class, 
package and local variable names.</li>
         <li>Member variables would be prefixed with m_</li>
         <li>Function parameter variables would be prefixed with p_</li>
         <li>Constants are capitalised eg CAPITALS_UNDERSCORES</li>
         <li>Global variables (should be avoided) would be prefixed with
g_<br>
         </li>
       
      </ul>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">5.6 In connection with exception handling, RC proposed 
using code reviews to influence each others style. He also noted that it is
important to aim for short functions to improve readibility.<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top"><b>6. Testing</b><br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">6.1 Testing requirements will come from the functional 
specification<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">6.2 The function specification must be tested against 
the requirements before continuing to the technical specification stage.<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">6.3 The technical specification must be tested agains 
the functional specification before continuing to the implementation stage.<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">6.4 Nominal unit testing is required for each class. 
It may be incomplete but if a bug is ever reported for the class, a test should
be added before the bug is fixed.<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">6.5 The system and functionality are to be tested 
against the function specification before deployment<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top"><b>7. Use case analysis</b><br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">7.1 The following list of potential actors was identified:<br>
       
      <ul>
         <li>Developer</li>
         <li>Project manager</li>
         <li>Tester</li>
         <li>Designed</li>
         <li>Analyst</li>
         <li>Sponsor/Client</li>
         <li>Call centre operator</li>
         <li>Help desk operator<br>
         </li>
       
      </ul>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
     <tr>
       <td valign="top">7.2 See addendum for use case diagrams Velocityme.zargo<br>
       </td>
       <td valign="top"><br>
       </td>
       <td valign="top"><br>
       </td>
     </tr>
       
  </tbody>  
</table>
  <br>
   
<table cellpadding="2" cellspacing="0" border="1" width="100%">
   <tbody>
     <tr>
       <th valign="top" bgcolor="#cccccc">Author<br>
       </th>
       <th valign="top" bgcolor="#cccccc">Date<br>
       </th>
       <th valign="top" bgcolor="#cccccc">Next Meeting<br>
       </th>
       <th valign="top" bgcolor="#cccccc">Venue<br>
       </th>
     </tr>
     <tr>
       <td valign="top">Robert Crida<br>
       </td>
       <td valign="top">2002-08-28<br>
       </td>
       <td valign="top">2002-09-03<br>
       </td>
       <td valign="top">13 Pearson Road<br>
 Tableview<br>
       </td>
     </tr>
   
  </tbody> 
</table>
 <br>
   <br>
</body>
</html>
